Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference
767-tree-1
name
1102
tree-preservation-order

undefined

767-tpo-1
uprn
address-text
point
POINT (-1.010870 50.886416)
geometry
MULTIPOLYGON (((-1.010799 50.886408,-1.010802 50.886422,-1.010812 50.886435,-1.010827 50.886445,-1.010847 50.886452,-1.010869 50.886454,-1.010891 50.886452,-1.010911 50.886446,-1.010927 50.886436,-1.010937 50.886424,-1.010941 50.886410,-1.010938 50.886396,-1.010928 50.886383,-1.010913 50.886373,-1.010893 50.886366,-1.010871 50.886364,-1.010849 50.886366,-1.010829 50.886372,-1.010813 50.886382,-1.010803 50.886395,-1.010799 50.886408)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL